Telematics integration enabling indexing and viewing of associated event videos

ABSTRACT

A system for telematics integration includes a video system configured to receive an event email notification from a telematics system. The telematics system was provided an email address for the event email notification. The video system is further configured to scrape the event email notification for event information and to determine whether event information satisfies criteria to generate trigger criteria for an event of interest. Then video system is further configured to, in the event that the event information satisfies the criteria to generate the trigger criteria, retrieve associated video from a video repository of the video system based at least in part on the trigger criteria.

BACKGROUND OF THE INVENTION

Currently integrations between video services and telematics solutionsare built in a one-to-one approach using application peripheralinterface (API) integrations between the telematics applications and thevideo services application. This legacy approach is time consuming,requires custom development for every pair-wise integration, and alsorequires access and licensing of APIs from the vendors of both video andtelematics platforms. The integrations have to be specified in detailand, once developed, require significant effort to maintain or to makeany changes.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a diagram illustrating an embodiment of a system fortelematics integration.

FIG. 2A is a diagram illustrating an embodiment of a video system.

FIG. 2B is a diagram illustrating an embodiment of a vehicle system.

FIG. 3 is a flow diagram illustrating an embodiment of a process fortelematics integration system.

FIG. 4 is a flow diagram illustrating an embodiment of a process forindicating to a telematics system to notify video system of events.

FIG. 5 is a flow diagram illustrating an embodiment of a process forscraping a notification.

FIG. 6 is a flow diagram illustrating an embodiment for a process forsatisfying a criteria to generate a trigger criteria.

FIG. 7 is a flow diagram illustrating an embodiment for a process forretrieving an associated video.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

A system for telematics integration is disclosed. The system comprises avideo system configured to receive an event email notification from atelematics system. The telematics system was provided an email addressfor the event email notification. The video system is configured toscrape the event email notification and determine whether eventsatisfies criteria to generate trigger criteria for an event ofinterest, and retrieve associated video from a video repository of thevideo system based at least in part on the trigger criteria in the eventthat the event satisfies the criteria to generate the trigger criteria.

The telematics integration system leverages the universal existence ofan e-mail notification engine in telematics applications as the sourcefor video-telematics integration meta-data. The notification engine ishistorically used to notify users of the telematics platform of a clientspecified event by sending an e-mail notification to a designatedrecipient list when client specified conditions are met. The telematicsintegration system utilizes the addition (e.g., by the systemconfiguration or by the client) of a generic e-mail addressed to thee-mail integration service, any time a video recording of the desiredevent is needed or wanted. The telematics integration system receivesevent meta-data via e-mail notification and scrapes pertinentinformation (e.g., vehicle ID and timestamp of an event) from the e-mailin order to generate a trigger for obtaining videos related to theevent. This allows a user of a telematics system to easily specify theconditions in which video is to be captured/indexed/uploaded for avisual recording of the desired event. In various embodiments, thetelematics system comprises a vehicle tracking system, a vehiclemonitoring system, a delivery management system, logistic managementsystem, fleet management system, fuel card system, or any other systemassociated with vehicles. The system qualifies events by providingconditions for events to the telematics system for a first level ofchecking and then a second level of checking to determine whether atrigger criteria is satisfied for retrieving data from a vehicle systemand/or a video system storage. In some cases, one of these checks isomitted and the video is retrieved based on only one condition, In somecases, the criteria is/are modified at the telematics system or at thevideo system using feedback after consistency check information does notpass one or more times.

The value of this system is that it provides for the development of atelematics integration system that easily and rapidly integrates betweenany telematics (or other operational platform) with a video service. Italleviates the need for time-consuming API-based one-to-one integrationsthat cannot cost-effectively be developed in sufficient numbers toreasonably span the spectrum of available telematics platforms inexistence.

FIG. 1 is a diagram illustrating an embodiment of a system fortelematics integration. In the example shown, a vehicle system (e.g.,vehicle system 108, vehicle system 110, and vehicle system 112) providesdata regarding driving routes, vehicle state, driving data, videostreams, images, vehicle sensor data to video system 100 and/or to atelematics system (e.g., telematics system 104 or telematics system 106)using cellular network 116 and/or network 102. In various embodiments,network 102 comprises a wired network, a wireless network, the Internet,a local area network, a combination of networks, or any otherappropriate combination of communication systems. User system 114 isinformed of events that occur as gleaned from the data received by videosystem 110 or the telematics systems. In order to properly determineevents, a full set of data is analyzed by one system. The telematicssystems are configured to provide notification to video system 100. Thesystem enables easier integration and swifter adaptation to changes bythe telematics systems by integrating a telematics system using email asthe notification mechanism. A telematics system is configured to sendthe notification in the event that specified circumstances are satisfiedand data regarding the event are emailed to video system 100. Thenotification received by video system 100 is parsed to extractinformation about the event (e.g., template identifier, pertinentinformation identifier, sender information, customer information, timestamp, vehicle identifier, location of event, etc.). A check is made asto whether the event information is relevant to video server 100 (e.g.,is customer relevant? is vehicle relevant? is location relevant? etc.).Video server 100 then determines whether the event satisfies criteria togenerate trigger criteria for an event of interest. In the event thatthe event satisfies the criteria to generate the trigger criteria,associated video is retrieved from a video repository of video system100 based at least in part on the trigger criteria. The trigger criteriamay also be generated using sensor information from a vehicle (e.g.,vehicle system 108, vehicle system 110, or vehicle system 112) or fromother telematics systems.

FIG. 2A is a diagram illustrating an embodiment of a video system. Insome embodiments, video system 200 is used to implement video system 100of FIG. 1. In the example shown, video system 200 includes processor204, interface 202, and video repository 206. Processor 204 includesscraper 208 and trigger determiner 210. Interface 202 receivesnotification from a telematics system and provides to scraper 208 ofprocessor 204. Scraper 208 determines information regarding an eventassociated with the notification. The information is provided to triggerdeterminer 210 to use in determining a trigger for videos relevant to anevent of interest. The trigger is used to search video repository 206for videos associated with the trigger (e.g., a location, a time, avehicle, etc. associated with the event of interest). Index 212 of videorepository 206 is used to find appropriate videos stored in storage 214of video repository 206. Also, if appropriate, processor 204communicates with vehicle(s) to identify video(s) relevant to triggerusing cellular network interface 216, which includes a cellulartransmitter/receiver, and retrieves appropriate video(s). Retrievedvideo(s) may be indexed and stored in video repository 206. Theappropriate videos from the repository and retrieved from vehicle(s) arereturned via interface 202 to a user using a user system.

FIG. 2B is a diagram illustrating an embodiment of a vehicle system. Invarious embodiments, vehicle system 250 is used to implement vehiclesystem 108, vehicle system 110, and/or vehicle system 112 of FIG. 1. Inthe example shown, vehicle system 250 measures a vehicle using sensorswhile being driven—for example, using acceleration sensor 260, videosensor 266, global positioning system (GPS) 268, camera 270, or anyother appropriate sensor. In some cases, video sensor 266 or camera 270are one of a plurality of video sensors or one of a plurality ofcameras. In some embodiments, video sensor 266 and camera 270 areintegrated into one physical unit. The data from the sensors is used todetect events by event detection 258 of processor 254. Vehicle system250 also receives information from vehicle sensors via a vehicle bus andvehicle interface 252. Data from the sensors associated with events isstored in storage 264 of event storage 256 and indexed in index 262. Insome cases, vehicle system 250 is connected to a network—for example, awired connection or a wireless network (e.g., local hot spot in avehicle depot yard)—for example, via interface 253. The event data issent to (e.g., either pushed or requested from) a video system usingcellular network interface 272, which includes a cellulartransmitter/receiver. In some cases, the video system desires videosassociated with an event of interest as defined using a trigger criteriaand a request is made for videos or other event data associated with thetrigger criteria. The processor searches stored event data in eventstorage 256 using index 262 and retrieves data/videos and provides themto a video system via the cellular network.

FIG. 3 is a flow diagram illustrating an embodiment of a process fortelematics integration system. In some embodiments, the process of FIG.3 is executed using a video system (e.g., video system 100 of FIG. 1).In the example shown, in 300 it is indicated to a telematics system tonotify a video system of events. For example, the telematics system isconfigured to notify the video system using an email notification systemin the event that an event at a telematics system is detected, where theevent is also configured to be of a character as defined by eventparameters. In some embodiments, the telematics system has default eventtypes that are sent as notifications. In some embodiments, othernotifications are also sent that are not events and these notificationswill be filtered out for video retrievals. In 302, an event emailnotification is received. For example, the telematics system emailsinformation about an event to a video system (e.g., a telematicsintegration system). In 304, the event email notification is scraped.For example, information regarding an event is scraped from an emailfrom a telematics system. In some embodiments, the email is parsed forinformation relevant for determining a trigger for an event of interestwhich is used to located videos of interest. In 306, it is determinedwhether an event satisfies criteria to generate trigger criteria for anevent of interest. For example, even though conditions for an event aresatisfied at the telematics system, the event may not pass consistencychecks or may not also satisfy other criteria to retrieve video data(e.g., the event is no longer of interest, not of the right type,already sufficiently investigated, needs to be qualified by some othercriteria, is not in the correct location, is not at the correct time, isnot associated with an appropriate vehicle, is not associated with anappropriate driver, etc.). In the event that the event does not satisfycriteria to generate trigger criteria for event of interest, the processends. In the event that the event does satisfy criteria to generatetrigger criteria for event of interest, the control passes to 308. In308, associated video events are retrieved using the trigger criteria.For example, a video repository is searched using an index for videos tobe retrieved based on trigger criteria for events of interest. Invarious embodiments, trigger criteria include a location associated withan event of interest, a time associated with an event of interest, avehicle associated with an event of interest, a customer associated withan event of interest, or any other appropriate criterion associated withan event of interest.

FIG. 4 is a flow diagram illustrating an embodiment of a process forindicating to a telematics system to notify video system of events. Insome embodiments, the process of FIG. 4 is used to implement 300 of FIG.3. In the example shown, in 400 a notification email address isprovided. For example, an email address is provided to a telematicssystem for notification to a video system. In 402, conditions for eventsare provided. For example, a telematics system is provided with criteriafor events that are interesting to the video system and what thetelematics system should be notifying the video system about. In someembodiments, no conditions are provided and this step is omitted. Insome embodiments, the telematics system automatically providesnotification to an email address regarding predetermined events asdetermined using predetermined criteria for events. In 404, anindication is received that the notification request was accepted. Forexample, the telematics system provides confirmation that emailnotification and/or conditions for events was received and accepted.

FIG. 5 is a flow diagram illustrating an embodiment of a process forscraping a notification. In some embodiments, the process of FIG. 5 isused to implement 304 of FIG. 3. In the example shown, in 500 atelematics platform is determined. For example, the identity of thetelematics system is determined from the notification (e.g., using aknown set of characteristics of the notification—for example, a patternor known text within the notification). In 502, a customer and/orassociated vehicle are determined. For example, the notification isparsed to determine a customer and/or associated vehicle. In someembodiments, the customer is determined from a vehicle identifier byretrieving a customer associated with a vehicle identifier from adatabase. In 504, it is determined whether an ID is associated with adetermined customer and/or vehicle. For example, the system determinesan identifier indicating whether the notification is relevant to thesystem or not. In the event that there is not an ID associated with adetermined customer and/or vehicle, then in 506 it is indicated thatthere is not an associated ID and the process ends. In the event thatthere is an ID associated with a determined customer and/or vehicle,then in 508 an associated time stamp and/or location are determined. Forexample, the time stamp of an event and/or location are determined fromthe information in the notification. In 510, it is determined whetherthe time stamp and/or location are with bounds. For example, it isdetermined whether the time stamp is within a time and/or date window(e.g., after a starting time limit and before and ending time limit),and/or the location is within a bounded set of location boundaries(e.g., within a radius from a point or within a set of boundary lines ordelineating points in any appropriate shape). In various embodiments,the time stamp is checked to see if it is within bounds, the location ischecked to see if it is within bounds, or the location and the timestamp are checked to see if they are within bounds. In the event thatthe time stamp and/or the location is not within bounds, in 512 it isindicated that the time stamp and/or location are not within bounds andthe process ends. In the event that the time stamp and/or the locationis within bounds, in 514 it is determined whether the information passesa consistency check. For example, the information is checked to see ifthe information is consistent with prior information received regardingthe same vehicle and/or customer (e.g., similar travel locations/timesfor the same vehicle and/or customer, etc.). In the event that theinformation does not pass a consistency check, in 516 it is indicatedthat the information does not pass the consistency check, and theprocess ends. In some cases, in the event that the information does notpass a consistency check or does not pass multiple consistency checks(e.g., a counter is incremented each time a check is not passed and uponthe counter exceeding a threshold value, the event conditions arechanged as provided to the telematics system). In the event that theinformation does pass a consistency check, in 518 the scrapedinformation is provided, and the process ends.

In various embodiments, scraped information comprises one or more of thefollowing: company source, fleet, vehicle type, vehicle identifier,vehicle description, driver, event type (e.g., cornering, hardcornering, braking, hard braking, etc.), time, location, latitude,longitude, speed, heading, satellites, vehicle state, registration, tripdistance, driver behavior, conditions for events, geofence information,operational data, or any other appropriate information.

FIG. 6 is a flow diagram illustrating an embodiment for a process forsatisfying a criteria to generate a trigger criteria. In someembodiments, the process of FIG. 6 is used to implement 306 of FIG. 3.In the example shown, in 600 an event of interest criteria is received.In 602, event information is received. In 604, it is determined whetherthe event information satisfies an event of interest criteria. In theevent that the event information does not satisfy an event of interestcriteria, in 606 no trigger criteria is indicated. In the event that theevent information does satisfy an event of interest criteria, in 608 atrigger criteria is determined based on the event information. Forexample, the trigger criteria comprise criteria for locating videosrelated to an event of interest (e.g., a location and time, an area anda time, a set of times and a set of locations, or any other appropriatecriteria). In some embodiments, the trigger criteria correspond to a setof vehicles in a location (e.g., all trucks in a loading yard).

FIG. 7 is a flow diagram illustrating an embodiment for a process forretrieving an associated video. In some embodiments, the process of FIG.7 is used to implement 308 of FIG. 3. In the example shown, in 700 indexof videos is searched using a trigger criteria. In 702, videos areretrieved from video storage using index results. In 704, it isdetermined whether videos should be retrieved from vehicle storage. Forexample, it is determined whether the system should contact one or morevehicle systems to retrieve videos. In the event that it is determinedthat videos should not be retrieved from vehicle storage, then controlpasses to 712. In the event that it is determined that videos should beretrieved from vehicle storage, then in 706 a vehicle is selected. In708, videos are retrieved from selected vehicle using trigger criteria.For example, the video data associated with the trigger criteria areretrieved from a vehicle system. In some embodiments, the video data isretrieved with associated metadata information—for example, a vehicleidentifier, a camera identifier, a timestamp, a location, a heading,etc. In 710, it is determined whether there are more vehicles. Forexample, it is determined whether there are more vehicles to retrievevideos from. In the event that there are more vehicles, then controlpasses to 706. In the event that there are not more vehicles, thencontrol passes to 712. In 712, videos are provided.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system for telematics integration, comprising:a processor; and a memory coupled with the processor, wherein the memoryis configured to provide the processor with instructions which whenexecuted cause the processor to: receive an event email notificationfrom a telematics system, wherein the telematics system was provided anemail address for the event email notification; scrape the event emailnotification for event information, comprising to: parse the event emailnotification for the event information, the event information includinga) an associated location, an associated time stamp, or a combinationthereof, and b) a vehicle identifier; determine whether the eventinformation passes a consistency check, comprising to: check to seewhether the event information is consistent with prior informationregarding the same vehicle, the same customer, or both; and in responseto a determination that the event information does not pass theconsistency check, indicate that the event information does not pass theconsistency check; determine whether the event information satisfiescriteria to generate trigger criteria for an event of interest, whereinthe trigger criteria comprises a trigger location and a trigger time, atrigger area and trigger time, or a set of trigger times and a set oftrigger locations, wherein the determining of whether the eventinformation satisfies criteria to generate trigger criteria for an eventof interest comprises to: perform three or more of the following: A)determine whether the event is no longer of interest; and in response toa determination that the event is no longer of interest, determine thatthe event information does not satisfy criteria to generate triggercriteria for the event of interest; B) determine whether the event isnot of the right type; and in response to a determination that the eventis not of the right type, determine that the event information does notsatisfy criteria to generate trigger criteria for the event of interest;C) determine whether the event is already sufficiently investigated; andin response to a determination that the event is already sufficientlyinvestigated, determine that the event information does not satisfycriteria to generate trigger criteria for the event of interest; D)determine whether the event is not in the trigger location or the set oftrigger locations; and in response to a determination that the event isnot in the trigger location or the set of trigger locations, determinethat the event information does not satisfy criteria to generate triggercriteria for the event of interest; and/or E) determine whether theevent is not at the trigger time; and in response to a determinationthat the event is not at the trigger correct time, determine that theevent information does not satisfy criteria to generate trigger criteriafor the event of interest; and in response to a determination that theevent information satisfies the criteria to generate the triggercriteria, retrieve associated video from a video repository based atleast in part on the trigger criteria, wherein the retrieving of theassociated video comprises to retrieve the associated video based onmetadata of the associated video, the metadata including a vehicleidentifier, a camera identifier, a timestamp, a location, a heading, orany combination thereof.
 2. The system as in claim 1, wherein the eventinformation comprises a customer identifier.
 3. The system as in claim1, wherein the event information comprises an associated vehicle.
 4. Thesystem as in claim 1, wherein the event information comprises theassociated time stamp.
 5. The system as in claim 1, wherein the eventinformation comprises the associated location.
 6. The system as in claim1, wherein the memory is further configured to provide the processorwith instructions which when executed cause the processor to: determinewhether the time stamp is within bounds.
 7. The system as in claim 1,wherein the memory is further configured to provide the processor withinstructions which when executed cause the processor to: determinewhether the location is within bounds.
 8. The system as in claim 1,wherein the trigger criteria comprise the trigger location.
 9. Thesystem as in claim 1, wherein the trigger criteria comprise the triggertime.
 10. The system as in claim 1, wherein the trigger criteriacomprise the trigger area.
 11. The system as in claim 1, wherein thetrigger criteria comprise the set of trigger locations.
 12. The systemas in claim 1, wherein the trigger criteria the set of trigger times.13. The system as in claim 1, wherein retrieving the associated videouses an index of videos.
 14. The system as in claim 1, wherein the emailevent notification is received from a telematics system.
 15. The systemas in claim 1, wherein retrieving the associated video is retrievingfrom one or more vehicle systems.
 16. The system as in claim 1, whereinthe determining of whether the event information satisfies criteria togenerate trigger criteria for an event of interest comprises to: performthe following: A) determine whether the event is no longer of interest;and in response to a determination that the event is no longer ofinterest, determine that the event information does not satisfy criteriato generate trigger criteria for the event of interest; B) determinewhether the event is not of the right type; and in response to adetermination that the event is not of the right type, determine thatthe event information does not satisfy criteria to generate triggercriteria for the event of interest; C) determine whether the event isalready sufficiently investigated; and in response to a determinationthat the event is already sufficiently investigated, determine that theevent information does not satisfy criteria to generate trigger criteriafor the event of interest; D) determine whether the event is not in thetrigger location or the set of trigger locations; and in response to adetermination that the event is not in the trigger location or the setof trigger locations, determine that the event information does notsatisfy criteria to generate trigger criteria for the event of interest;and E) determine whether the event is not at the trigger time; and inresponse to a determination that the event is not at the trigger correcttime, determine that the event information does not satisfy criteria togenerate trigger criteria for the event of interest.
 17. A method fortelematics integration, comprising: receiving an event emailnotification from a telematics system, wherein the telematics system wasprovided an email address for the event email notification; scraping,using a processor, the event email notification for event information,comprising: parsing the event email notification for the eventinformation, the event information including a) an associated location,an associated time stamp, or a combination thereof, and b) a vehicleidentifier; determining whether the event information passes aconsistency check, comprising: checking to see whether the eventinformation is consistent with prior information regarding the samevehicle, the same customer, or both; and in response to a determinationthat the event information does not pass the consistency check,indicating that the event information does not pass the consistencycheck; determining whether the event information satisfies criteria togenerate trigger criteria for an event of interest, wherein the triggercriteria comprises a trigger location and a trigger time, a trigger areaand trigger time, or a set of trigger times and a set of triggerlocations, wherein the determining of whether the event informationsatisfies criteria to generate trigger criteria for an event of interestcomprises: performing three or more of the following: A) determinewhether the event is no longer of interest; and in response to adetermination that the event is no longer of interest, determine thatthe event information does not satisfy criteria to generate triggercriteria for the event of interest; B) determine whether the event isnot of the right type; and in response to a determination that the eventis not of the right type, determine that the event information does notsatisfy criteria to generate trigger criteria for the event of interest;C) determine whether the event is already sufficiently investigated; andin response to a determination that the event is already sufficientlyinvestigated, determine that the event information does not satisfycriteria to generate trigger criteria for the event of interest; D)determine whether the event is not in the trigger location or the set oftrigger locations; and in response to a determination that the event isnot in the trigger location or the set of trigger locations, determinethat the event information does not satisfy criteria to generate triggercriteria for the event of interest; and/or E) determine whether theevent is not at the trigger time; and in response to a determinationthat the event is not at the trigger correct time, determine that theevent information does not satisfy criteria to generate trigger criteriafor the event of interest; and in response to a determination that theevent information satisfies the criteria to generate the triggercriteria, retrieving associated video from a video repository based atleast in part on the trigger criteria, wherein the retrieving of theassociated video comprises retrieving the associated video based onmetadata of the associated video, the metadata including a vehicleidentifier, a camera identifier, a timestamp, a location, a heading, orany combination thereof.
 18. A computer program product for telematicsintegration, the computer program product being embodied in anon-transitory computer readable storage medium and comprising computerinstructions for: receiving an event email notification from atelematics system, wherein the telematics system was provided an emailaddress for the event email notification; scraping, using a processor,the event email notification for event information, comprising: parsingthe event email notification for the event information, the eventinformation including a) an associated location, an associated timestamp, or a combination thereof, and b) a vehicle identifier;determining whether the event information passes a consistency check,comprising: checking to see whether the event information is consistentwith prior information regarding the same vehicle, the same customer, orboth; and in response to a determination that the event information doesnot pass the consistency check, indicating that the event informationdoes not pass the consistency check; determining whether the eventinformation satisfies criteria to generate trigger criteria for an eventof interest, wherein the trigger criteria comprises a trigger locationand a trigger time, a trigger area and trigger time, or a set of triggertimes and a set of trigger locations, wherein the determining of whetherthe event information satisfies criteria to generate trigger criteriafor an event of interest comprises: performing three or more of thefollowing: A) determine whether the event is no longer of interest; andin response to a determination that the event is no longer of interest,determine that the event information does not satisfy criteria togenerate trigger criteria for the event of interest; B) determinewhether the event is not of the right type; and in response to adetermination that the event is not of the right type, determine thatthe event information does not satisfy criteria to generate triggercriteria for the event of interest; C) determine whether the event isalready sufficiently investigated; and in response to a determinationthat the event is already sufficiently investigated, determine that theevent information does not satisfy criteria to generate trigger criteriafor the event of interest; D) determine whether the event is not in thetrigger location or the set of trigger locations; and in response to adetermination that the event is not in the trigger location or the setof trigger locations, determine that the event information does notsatisfy criteria to generate trigger criteria for the event of interest;and/or E) determine whether the event is not at the trigger time; and inresponse to a determination that the event is not at the trigger correcttime, determine that the event information does not satisfy criteria togenerate trigger criteria for the event of interest; and in response toa determination that the event information satisfies the criteria togenerate the trigger criteria, retrieving associated video from a videorepository based at least in part on the trigger criteria, wherein theretrieving of the associated video comprises retrieving the associatedvideo based on metadata of the associated video, the metadata includinga vehicle identifier, a camera identifier, a timestamp, a location, aheading, or any combination thereof.